• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    METHOD, COMPUTER DEVICE AND COMPUTER STORAGE MEDIA FOR FILE MANAGEMENT WITH RESERVED SPACE. The present invention pertains to aspects of the subject matter described herein that pertain to file system placeholders. In aspects, placeholders can be used by a client to represent remote file system objects. Placeholders can include metadata and can also include none, some, or all of the contents of the represented remote file system objects. In conjunction with the local file system metadata, placeholders allow a file system namespace to be browsed and can also allow other operations to be performed on file system objects even when the client is offline with respect to the file system. remote file system. After connectivity is re-established with the remote file system, placeholders can be used for synchronizing changes.
    公开号:BR112015027040B1
    申请号:R112015027040-9
    申请日:2013-09-18
    公开日:2022-01-25
    发明作者:Relja Ivanovic；Michael John Novak；Chris Guzak；Sangeeta Ranjit；Scott David Hoogerwerf；Amnon Itamar Govrin；Marc Wautier；Kiernon Reiniger；Ramanarayanan Ramani；Oded Yehuda Shekel
    申请人:Microsoft Technology Licensing, Llc；
    IPC主号:
    专利说明:

    BACKGROUND
    [001] It is currently not uncommon for a family or even a single person to have multiple computing devices such as a desktop computer, a laptop, a smartphone, an Internet-enabled television, a set-top box, a gaming device, a reading tablet. , and so on. Furthermore, a user may have thousands of files that include images, audio, documents, and the like that are stored in the cloud or elsewhere. A user may want to access files from one or more of the computing devices available to the user.
    [002] Downloading all user content to each of the user's devices may not be possible as some devices may have very limited storage. Furthermore, even when a computing device has extensive storage, downloading content to the computing device can consume considerable bandwidth, be costly, and take a long time.
    [003] The subject matter claimed here is not limited to modalities that resolve any drawbacks or that operate only in environments such as those described above. Instead, this background is only provided to illustrate an exemplary technology area where some of the modalities described here can be practiced. SUMMARY
    [004] In summary, aspects of the subject described here pertain to file system placeholders. In aspects, placeholders can be used by a client to represent remote file system objects. Placeholders can include metadata and can also include none, some, or all of the contents of the represented remote file system objects. In conjunction with local file system metadata, placeholders allow a file system namespace to be browsed and can also allow other operations to be performed on file system objects even when the client is offline with respect to the file system. remote file system. After connectivity is re-established with the remote file system, the placeholders can be used for synchronizing changes.
    [005] This Summary is provided to briefly identify some aspects of the matter which are further described in the Detailed Description below. This Summary is not intended to identify key or essential features of the claimed subject, nor is it intended to be used to limit the scope of the claimed subject.
    [006] The phrase "subject described herein" refers to the subject described in the Detailed Description unless the context clearly dictates otherwise. The term "aspects" should be read as "at least one aspect". Identifiable aspects of the subject matter described in the Detailed Description are not intended to identify key or essential features of the claimed subject.
    [007] The aspects described above and other aspects of the subject described herein are illustrated by way of example and are not limited to the accompanying figures in which like reference numbers indicate similar elements and in which: BRIEF DESCRIPTION OF THE DRAWINGS
    [008] Figure 1 is a block diagram representing an exemplary general-purpose computing environment in which aspects of the subject matter described herein can be incorporated;
    [009] Figures 2-3 are block diagrams that generally represent exemplary components of systems configured to use placeholders according to aspects of the subject described here;
    [0010] Figure 4 is a flowchart that generally represents exemplary actions that may occur from a customer perspective according to the aspects of the subject described here; and
    [0011] Figure 5 is a flowchart that generally represents exemplary actions that can occur from a cloud storage system perspective according to the aspects of the subject described here. DETAILED DESCRIPTION DEFINITIONS
    [0012] As used herein, the term "includes" and its variants should be read as open-ended terms meaning "includes, but is not limited to". The term "or" should be read as "and/or" unless the context clearly dictates otherwise. The term "based on" should be read as "based at least in part on". The terms "a modality" and "the modality" should be read as "at least one modality". The term "other modality" should be read as "at least one other modality".
    [0013] As used herein, terms such as "a", "an", and "the" are inclusive of one or more of the item or action indicated. Specifically, in claims a reference to an item generally means that at least one such item is present and a reference to an action means that at least one instance of the action is performed.
    [0014] Sometimes here the terms "first", "second", "third" and so on may be used. Without additional context, the use of these terms in the claims is not intended to imply an ordering but is instead used for identification purposes. For example, the phrases "first version" and "second version" do not necessarily mean that the first version is exactly the first version or was created before the second version or even that the first version is ordered or operated before the second version. Instead, these phrases are used to identify different versions.
    [0015] Headers are for convenience only: information about a given topic can be found outside the section whose header indicates that topic.
    [0016] Other definitions, explicit and implicit, may be included below. EXEMPLARY OPERATING ENVIRONMENT
    [0017] Figure 1 illustrates an example of a suitable computing system environment 100 in which aspects of the subject described herein can be implemented. The computing system environment 100 is only an example of a suitable computing environment and is not intended to suggest any limitations as to the scope of use or functionality of aspects of the subject matter described herein. Nor should the computing environment 100 be interpreted as having any dependency or requirement relating to one or a combination of components illustrated in the exemplary operating environment 100.
    [0018] Aspects of the subject described here are operational with numerous other general-purpose or special-purpose computing system environments or configurations. Examples of well-known computing systems, environments, or configurations that may be suitable for use with aspects of the subject matter described herein include personal computers, server computers - whether in pure metal or as virtual machines -, portable or laptop devices, multiprocessor, microcontroller-based systems, set-top boxes, programmable and non-programmable consumer electronics, network PCs, minicomputers, mainframe computers, personal digital assistants (PDAs), gaming devices, printers, equipment including a set top box, media center, or others equipment, computing devices built into or attached to automobiles, other mobile devices, telephone devices including cell phones, cordless phones, and corded phones, distributed computing environments that include any of the above systems or devices, and the like.
    [0019] Aspects of the subject described here can be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, components, data structures, and so on that perform specific tasks or implement specific abstract data types. Aspects of the subject described here can also be practiced in a distributed computing environment where tasks are performed by remote processing devices that are connected through a communications network. In a distributed computing environment, program modules can be located on both local and remote computer storage media including memory storage devices.
    [0020] Alternatively, or in addition, the functionality described here may be performed, at least in part, by one or more logical hardware components. For example, and without limitation, illustrative types of hardware logic components that may be used include Field Programmable Gate Networks (FPGAs), Program-Specific Integrated Circuits (ASICs), Program-Specific Standard Products (ASSPs), System Systems on a Chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
    [0021] With reference to Figure 1, an exemplary system for implementing aspects of the subject matter described herein includes a general purpose computing device in the form of a computer 110. A computer may include any electronic device that is capable of executing an instruction. Computer components 110 may include a processing unit 120, system memory 130, and one or more system buses (represented by system bus 121) that couple various system components including system memory in processing unit 120. System bus 121 can be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include an Industry Standard Architecture (ISA) bus, Microchannel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronic Standards Association (VESA) local bus, Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus, Extended Peripheral Component Interconnect (PCI-X) bus, Advanced Graphics Port (AGP), and PCI express (PCIe).
    [0022] The processing unit 120 may be connected to a hardware security device 122. The security device 122 may store and be able to generate cryptographic keys that can be used to protect various aspects of the computer 110. In one embodiment , security device 122 may comprise a Trusted Platform Module (TPM) chip, TPM Security Device, or the like.
    [0023] The computer 110 typically includes a variety of computer readable media. Computer readable media may be any available medium that is accessible by computer 110 and includes both volatile and non-volatile medium, and removable and non-removable medium. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media.
    [0024] Computer storage medium includes both volatile and non-volatile, removable and non-removable medium implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data . Computer storage media include RAM, ROM, EEPROM, solid state storage, flash memory or other memory technology, CD-ROM, digital versatile discs (DVD) or other optical disc storage, magnetic cassettes, magnetic tape, storage disk drives or other magnetic storage devices, or any other medium which may be used to store desired information and which may be accessed by the computer 110. The computer storage medium does not include a communication medium.
    [0025] The communication medium typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any means of providing information. The term "modulated data signal" means a signal that has one or more of its characteristics adjusted or changed in such a way as to encode the information in the signal. By way of example, and not limitation, the communication medium includes a wired medium such as a wired network or direct wired connection, and wireless medium such as an acoustic, RF, infrared, and other wireless medium. Combinations of any of the above must also be included in the scope of computer readable media.
    [0026] System memory 130 includes computer storage media in the form of volatile and/or non-volatile memory such as read-only memory (ROM) 131 and random access memory (RAM) 132. An input system / basic output 133 (BIOS), which contains the basic routines that help transfer information between elements within the computer 110, such as during startup, is typically stored in ROM 131. RAM 132 typically contains data and/or modules that are immediately accessible to and/or currently being operated by the processing unit 120. By way of example, and not limitation, Figure 1 illustrates the operating system 134, application programs 135, other program modules 136, and data from program 137.
    [0027] Computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media. As an example only, Figure 1 illustrates a hard disk drive 141 that reads from or writes to non-removable, non-volatile magnetic media, magnetic disk drive 151 that reads from or writes to a removable, non-volatile magnetic disk 152, and a optical disk drive 155 that reads from or writes to a removable, non-volatile optical disk 156 such as a CD ROM, DVD, or other optical medium. Other removable/non-removable, volatile/non-volatile computer storage media that may be utilized from the exemplary operating environment include magnetic tape cassettes, flash memory cards, and other solid-state storage devices, digital versatile disks, other disks optics, digital video tape, solid-state RAM, solid-state ROM, and the like. Hard disk drive 141 may be connected to system bus 121 via interface 140, and magnetic disk drive 151 and optical disk drive 155 may be connected to system bus 121 by an interface for nonvolatile removable memory such as like interface 150.
    [0028] The units and their associated computer storage medium, discussed above and illustrated in Figure 1, provide storage of computer-readable instructions, data structures, program modules, and other data for the computer 110. In Figure 1, for example, hard disk drive 141 is illustrated as storing operating system 144, application programs 145, and other program modules 146, and program data 147. Note that these components may be either the same as or different. operating system 134, application programs 135, other program modules 136, and program data 137. Operating system 144, application programs 145, other program modules 146, and program data 147 are given different numbers here to illustrate at the very least, these are different copies.
    [0029] A user may enter commands and information into the computer 110 through input devices such as a keyboard 162 and a pointing device 161, commonly referred to as a mouse, trackball, or touch panel. Other input devices (not shown) may include a microphone (eg, for inputting voice or other audio), joystick, gamepad, satellite dish, scanner, a touchscreen, a writing tablet, a camera ( for example, to enter gestures or other visual input), or the like. These and other input devices are often connected to the processing unit 120 through a user input interface 160 that is coupled to the system bus, but may be connected through other interfaces and bus structures, such as a parallel port, gamepad or a universal serial bus (USB).
    [0030] By using one or more of the above-identified input devices a Natural User Interface (NUI) can be established. A NUI, can be based on voice recognition, touch and pen recognition, gesture recognition both on the screen and adjacent to the screen, gestures in the air, head and eye tracking, voice and speech, vision, touch, gestures, machine, and the like. Some exemplary NUI technologists that can be employed to interact with a user include touch displays, speech and voice recognition, understanding of intent and purpose, motion gesture detection utilizing depth cameras (such as stereoscopic camera systems, infrared camera systems, RGB camera systems, and combinations thereof), motion gesture detection using accelerometers/gyroscopes, facial recognition, 3D displays, head, eye, and gaze tracking, immersive augmented reality and virtual reality systems, as well as technologies to detect brain activity using electric field detection electrodes (EEG and related methods).
    [0031] A monitor 191 or other type of display device is also connected to the system bus 121 through an interface, such as a video interface 190. In addition to the monitor, computers may also include other peripheral output devices such as speakers 197 and printer 196, which can be connected via a peripheral output interface 195.
    [0032] Computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as remote computer 180. Remote computer 180 may be a personal computer, a server, a router, a network PC , a point device or other common network node, and typically includes many or all of the elements described above in relation to computer 110, although only memory storage device 181 has been illustrated in Figure 1. The logical connections shown in Figure 1 includes a local area network (LAN) 171 and a wide area network (WAN) 173, but may also include telephone networks, near-field networks, and other networks. Such networked environments are common in office, enterprise-wide computer networks, intranets, and the Internet.
    [0033] When used in a LAN network environment, computer 110 is connected to LAN 171 through a network interface or adapter 170. When used in a WAN networked environment, computer 110 may include a modem 172 or other means to establish communications over WAN 173, such as the Internet. Modem 172, which may be internal or external, may be connected to system bus 121 through user input interface 160 or other appropriate mechanism. In a networked environment, program modules presented in relation to the computer 110, or portions thereof, may be stored on the remote memory storage device. By way of example, and not limitation, Figure 1 illustrates remote application programs 185 as residing in memory device 181. It will be appreciated that the network connections shown are exemplary and other means for establishing a communications connection between computers may be used. RESERVED SPACES
    [0034] According to one aspect of the subject described here, placeholders may be used. A placeholder can include a data structure that represents a file system object. A file system object can be a file or a directory. A directory can include zero or more files and can be a traditional file directory or some other collection or container of files. For simplicity, the term archive is often used here, but it should be understood that the teachings here can also be applied to directories without departing from the spirit or scope of aspects of the subject matter described herein.
    [0035] A placeholder can be stored on a machine's local storage device. In one implementation, a placeholder may indicate that the content associated with the placeholder is available in a location other than a machine file system (hereinafter sometimes referred to as a local file system or a client file system). ). For example, a placeholder might indicate that the content associated with the placeholder is stored on one of the cloud storage systems illustrated in Figure 3.
    [0036] In another implementation, a placeholder may indicate that the content is accessible through an application residing on the machine. This application can store the content in memory, a local file system or a remote file system, it can generate the content, it can execute a combination of the above, or similar. Even if the file system could get the content directly, the file system can still rely on the application to access the content of the file.
    [0037] In one implementation, for a placeholder where the associated content is relatively small (e.g., less than a predetermined, configured, or calculated threshold), a copy of the entire content associated with the placeholder may also be stored in the reserved space. Storing data "in placeholder" means including storing the data in the placeholder data structure and/or storing the data in a local storage location indicated by the placeholder.
    [0038] Depending on the implementation, a placeholder can include various levels of detail about a file. At a minimum, a placeholder includes data that identifies a file on a remote storage system. For example, a placeholder might indicate a specific cloud storage system where content can be found along with information (eg an identifier) that identifies the file to the cloud storage system.
    [0039] A placeholder can include extrinsic metadata and/or intrinsic metadata of a file. Extrinsic metadata is any metadata that is stored outside the contents of the file. For example, extrinsic metadata may include name, size, modified data, created data, last accessed data, file attributes, version, other metadata maintained by the file system, and the like.
    [0040] Intrinsic metadata is any metadata that is stored within the contents of the file. For example, for an audio file, the intrinsic metadata may include artist name, album name, year, song title, rating, tags, comments, genre, length, encore rate, and the like. For an image such as a camera image, the intrinsic metadata may include, for example, author, data made, acquisition program name, dimensions, resolution, bit depth, compression, camera manufacturer, camera model, aperture, exposure time, other information, and the like.
    [0041] The examples of intrinsic and extrinsic metadata described above are not intended to be fully inclusive or exhaustive of the types of extrinsic metadata. Indeed, based on the teachings herein, those skilled in the art will readily recognize other extrinsic and intrinsic metadata that can be used in accordance with the teachings herein without departing from the spirit or scope of aspects of the subject matter described herein.
    [0042] In an implementation, a placeholder can include extrinsic metadata of a file such as the name of the file, the size of the file, a data that the file was modified, and a data that the file was created. In another implementation, in addition to the above, a placeholder may also include file attributes.
    [0043] In another implementation, a placeholder may include some or all of a file's intrinsic metadata.
    [0044] In one implementation, a placeholder can include some or all of the searchable text of a file. For example, a word processing document might have content that includes text and formatting. A placeholder can include the leading N characters, words, paragraphs, pages, or the like of the unformatted word processing document text, where N is predetermined, configurable, or dynamically determined.
    [0045] In an implementation, a placeholder may include an indication of the language(s) of the searchable text. For example, a placeholder can include data indicating that the searchable text is written in English. As another example, a placeholder may include data (e.g. an identifier or other data) that indicates that a portion of text is written in English and data (e.g., another identifier or other data) that indicates that another portion of text is written in English. is written in Spanish.
    [0046] As another example, a presentation program may have relatively little text compared to other data used for a presentation. In this example, a placeholder can include the entire text of the presentation while omitting other data used for the presentation.
    [0047] In one implementation, a placeholder can include a thumbnail of an image. The image can be included in the file content associated with the placeholder while the thumbnail can be generated from the image or also included in the file content. In one embodiment, the thumbnail included in the placeholder can be of a relatively small size that can be predefined, configurable, or dynamically determined.
    [0048] In one implementation, a placeholder may include data that identifies how to obtain larger thumbnails of the content associated with the placeholder. For example, a placeholder might include an address of a service from which a larger thumbnail of a file might be requested. The service may be able to accept an input that indicates the size of the thumbnail that should be provided.
    [0049] Likewise, in one implementation, a placeholder may include a lower fidelity sample (or data identifying how to sample it) of content from a file associated with the placeholder. For example, a placeholder might include a lower fidelity sample (or connection to a service) of a song, video, or other file type.
    [0050] In one implementation, a placeholder may include a data structure (eg, a bitmap, connected list, or other data structure) that indicates what portions of the associated content are located in the local file system. This data structure can be consulted when a program seeks to access the content. If the data structure indicates that the requested content is available locally, the requested content can be retrieved from local storage. If not, other actions can be taken to get the requested content from remote storage before providing the program with the content.
    [0051] In one implementation, a placeholder may have a flag that indicates whether the contents of the file should be made available when offline. As previously indicated, a client may periodically lose connectivity to remote storage during which content associated with a placeholder is found. If the flag is set, when the client is online, the content for the placeholder can be downloaded to local storage and kept there so that the content is available even when remote storage is unavailable.
    [0052] Various embodiments may have placeholders that include any one or more of the above data.
    [0053] A placeholder can be used to give the illusion that a file resides on a local file system even when the file's contents reside remotely. This illusion can be maintained even when the remote file system is not reachable. This can be done by inserting the space into a namespace of a local file system. The file system can be modified to recognize placeholders and display information about a file represented by the placeholder as appropriate. For example, the file system might display the names and metadata relevant to a placeholder when a user browses through the local file system's namespace.
    [0054] Placeholders can be used to vastly reduce the amount of space consumed. For example, instead of storing content for large videos locally, placeholders can be used to indicate that videos are available. Because placeholders can use a much smaller amount of space than the actual video content, even a relatively small local storage device can include placeholders for a vast collection of files that include a significant amount of content.
    [0055] Placeholders can be used when a remote storage system is unavailable. For example, when network connective is lost or unavailable, a machine can use locally stored placeholders to browse and perform other operations in a file system's namespace.
    [0056] A placeholder is persisted even when the client machine is powered off. Thus, the placeholder is still available when the client machine is restarted. This persistent behavior can be implemented by storing the reserved space on a client's local storage.
    [0057] Figures 2-3 are block diagrams that generally represent components of exemplary systems configured to use placeholders according to aspects of the subject described here. The components illustrated in Figures 2-3 are exemplary and are not intended to be fully inclusive of components that may be required or included. Furthermore, the number of components may differ in other embodiments without departing from the spirit or scope of aspects of the subject described herein. In some embodiments, the components described in conjunction with Figures 23 may be included in other components (shown or not shown) or placed in subcomponents without departing from the spirit or scope of aspects of the subject matter described herein. In some embodiments, the components and/or functions described in conjunction with Figures 2-3 may be distributed across multiple devices.
    [0058] As used herein, the term component shall be read to include hardware such as all or a portion of a device, a collection of one or more software modules or portions thereof, some combination of one or more software modules or portions thereof and one or more devices or portions thereof, and the like.
    [0059] For example, the components illustrated in Figures 2-3 can be implemented using one or more computing devices. Such devices may include, for example, personal computers, server computers, handheld or laptop devices, multiprocessor systems, microcontroller-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, cell phones, personal assistants digital devices (PDAs), gaming devices, printers, equipment that includes a set top box, media center, or other equipment, in-car or embedded computing devices, other mobile devices, distributed computing environments that include any of the systems or devices, and the like.
    [0060] An exemplary device that may be configured to implement one or more of the components of Figures 2-3 comprises the computer 110 of Figure 1.
    [0061] A component may also include or be represented by a code. The code includes instructions that indicate the actions a computer should take. The code may also include information other than actions the computer must take such as data, resources, variables, definitions, relationships, associations, and the like.
    [0062] The code can be executed by a computer. When code is executed by a computer, it can be called a process. The term "process" and its variants as used herein may include one or more traditional processes, threads, components, libraries, objects that perform tasks, and the like. A process can be implemented in hardware, software, or a combination of hardware and software. In one embodiment, a process is any mechanism, however called, capable of or used in performing an action. A process can be distributed over multiple devices or a single device. The code can run in user mode, kernel mode, some other mode, a combination of the above, or the like.
    [0063] Returning to Figure 2, the system 200 may include a client 205, a remote storage system 210, a local storage 215, a placeholder 220, and may include other components (not shown). The client 205 may have direct access to the local storage 215 and be connected to the remote storage system 210 through the use of a cloud network.
    [0064] Although the terms "client" and "server" are sometimes used here, it should be understood that a client can be implemented on a machine that has hardware and/or software that is typically associated with a server and that likewise, a server can be implemented on a machine that has hardware and/or software that is typically associated with a desktop, personal, or mobile computer. Furthermore, a client can sometimes act as a server and vice versa. Sometimes, two or more entities that most often act as a client or server may concurrently be peers, servers, or clients. In one embodiment, a client and server may be implemented on the same physical machine.
    [0065] Further, as used herein, each of the terms "server" and "client" may refer to one or more physical or virtual entities, one or more processes running on one or more physical or virtual entities, and the like. Thus, a server can include a real physical node on which one or more processes run, a virtual node on which one or more processes run, a service running on one or more nodes, a group of nodes that together provide a service, and the like. A service can include one or more processes that run on one or more physical or virtual entities. Furthermore, a single process may implement one or more servers.
    [0066] Local storage 215 can include any storage media capable of storing data. For example, local storage 215 may include volatile memory (eg, a cache) and non-volatile memory (eg, persistent storage). The term data should be read broadly to include anything that can be represented by one or more computer storage elements. Logically, data can be represented as a series of 1's and 0's in volatile or non-volatile memory. On computers that have a non-binary storage medium, data can be represented according to the capabilities of the storage medium. Data can be organized into different types of data structures including simple data types such as numbers, letters, and the like, hierarchical, connected, or other related data types, data structures that include multiple other data structures or data types. simple data, and the like. Some examples of data include information, program code, program status, program data, other data, and the like.
    [0067] Local storage 215 can be external or internal or include some components that are internal and some components that are external to the client 205. In one implementation, local storage 215 can include any storage that is housed on a machine hosting the client 205. In another implementation, local storage 215 may include storage that is directly connected to the machine hosting the client 205. For example, local storage 215 may be connected to the machine via a USB connection, an IEEE 1394 connection, an optical connection, another wired connection, or the like.
    [0068] Remote storage system 210 may include one or more computers that are arranged to store and provide access to data. Access as used herein may include reading data, writing data, erasing data, updating data, a combination that includes two or more of the above, and the like. Remote storage system 210 may be connected to client 205 via a network such as the cloud. The cloud is a term that is often used as a metaphor for the Internet. It creates the idea that computing, software, data access, storage, and other resources can be provided by entities connected to the Internet without requiring users to know the location or other details about the computing infrastructure that provides these resources.
    [0069] In one example, the remote storage system 210 may comprise a data center where computing devices are located in a single physical location. In another example, remote storage system 210 may include computing and storage devices that are attached to the cloud in different locations. In one example, remote storage system 210 may comprise a single server or other computing device that provides access to one or more storage devices. In one example, remote storage system 210 may comprise a computing device that is not on the local area network (LAN) of client 205. In another example, remote storage system 210 may comprise any storage that is not housed in or directly connected to the client 205. In another example, the remote storage system 210 may include storage that is not available to the client 205 when the client is not connected to a network from which the storage is accessible.
    [0070] The term cloud storage system is sometimes used here. This is not intended to be limiting with respect to remote storage systems to which the teachings herein may apply but to provide an example of a remote storage system that may be used without departing from the spirit or scope of aspects of the subject matter described herein. Whenever the term cloud storage system is used herein, it should be understood that in other embodiments, other types of remote storage system may be used without departing from the spirit or scope of aspects of the subject matter described herein.
    [0071] While local storage 215 may be almost continuously available to the client 205 or may be readily made available by means available to the user (e.g., by plugging into a connector) the remote storage system 210 may sometimes make becomes unavailable to client 205. For example, if client 205 is hosted on a laptop, the laptop can be moved to a location that does not have access to the Internet. As another example, network outages can disrupt connectivity from the client 205 to the remote storage system 210. As another example, the remote storage system 210 can become inoperable or it can be shut down or disconnected for maintenance or other purposes. Without placeholders, when connectivity to remote storage system 210 is lost, client 205 may not be able to browse the namespace or perform operations on a file where the entire file content is not available on local storage 215.
    [0072] Placeholder 220 illustrates several exemplary data fields that can be stored in a placeholder stored in local storage 215. Although only one placeholder is shown in Figure 2, more often than not, there were multiple placeholders stored in local storage. 215. For example, for a given namespace, there may be a placeholder for each remote file system object if the contents of the remote file system object do not completely exist in local storage 215. As another example, for the data namespace, placeholders for remote file system objects may also exist even when the entire contents of the remote file system objects exist in local storage 215. This second set of placeholders may also be stored in local storage 215 for files that have content with a size smaller than a given threshold as previously mentioned.
    [0073] A namespace may include an identifier (eg, name or other identifier) for each file in a file system along with hierarchy information pertaining to the file. For example, a namespace might include a namespace entry that corresponds to D:DIR1FILE1.TXT. This namespace entry indicates the name of a file (eg FILE1.TXT) and indicates that the file exists in a directory (eg DIR1). The namespace can also include other metadata. A namespace can have a one-to-one or some mapping with file system information and can represent virtual folder hierarchies.
    [0074] Referring to Figure 3, the system 300 may include a client 305, a cloud 310, cloud storage systems 315-317, a local storage 320, an operations log 321, and other components (not shown). the client 305 may include a file manager 325, a synchronization manager 326, a placeholder manager 327, and other components (not shown).
    [0075] The components of Figure 3 can be implemented using the hardware and/or software of one or more computing devices as previously described. Storage devices implementing local storage 320 and logging operations 321 may be implemented in a similar fashion to local storage 215 of Figure 2 and may be external, internal, or include some components that are internal and some components that are external to the customer 305.
    [0076] Local storage 320 may have computer storage elements that maintain file system metadata for local file system objects from a client's local file system and that maintain placeholders for remote file system objects from a cloud storage system. As previously mentioned, placeholders can include metadata of remote file system objects without requiring the contents of remote file system objects to exist in local storage 320.
    [0077] Operations log 321 may have computer storage elements that hold data regarding changes that occur in the local file system. The 321 transaction log data can be used to synchronize these changes with cloud storage systems. In an implementation, the 321 operations log can be omitted and changes to the local file system can be discovered by comparing the state before the changes to the state after the changes to the local file system.
    [0078] The 325 file manager can be structured to create, through the file system metadata and placeholders, a namespace that includes both the local file system objects and the remote file system objects. The file manager 325 can be further structured to provide, through an interface, metadata for the local file system objects and the remote file system objects regardless of whether connectivity exists with the cloud storage system.
    [0079] In the absence of connectivity to a cloud storage system, the 325 file manager may still allow operations to proceed on both files residing locally and files represented by placeholders. For example, the file manager can update a file system data structure of the local file system to indicate an operation performed on a file system object represented by a placeholder even when the contents of the file system object are not completely resides on local storage. As another example, the file manager 325 may update a namespace to reflect an operation such as a rename, move, delete, restore, create, copy, or similar operation.
    [0080] The 326 synchronization manager can be structured to discover changes (e.g. content changes, metadata changes including intrinsic, extrinsic, and namespace changes, other similar changes) that have occurred to file system objects in the absence of cloud storage system connectivity and, when connectivity is re-established with the cloud storage system, to synchronize changes with the cloud storage system.
    [0081] In different implementations, the 326 synchronization manager may use various methods to discover the changes. For example, in one implementation, the synchronization manager 326 can discover changes by examining the log of operations 321. As another example, in another implementation, the synchronization manager 326 can discover changes by comparing a file system state and file system objects. file before changes with a file system state and file system objects after changes.
    [0082] The 327 placeholder manager can be structured to create, distribute, and maintain placeholders to ensure that a placeholder exists for each remote file system object in the namespace at least if the system object's contents file system does not completely exist on local storage 320. As previously mentioned, a placeholder can also be kept on the local file system when the contents of the remote file system object exist completely on local storage 320.
    [0083] Cloud storage systems 315-317 may include one or more storage devices together with one or more computing devices to provide access to those storage devices. In one embodiment, a cloud storage system may comprise a data center where computing devices are located at a single physical location. In another embodiment, a cloud storage system may include computing and storage devices that are attached to the cloud in different locations. In one embodiment, a cloud storage system may comprise a single server that provides access to one or more storage devices. In one embodiment, a cloud storage system may comprise a computing device that is not on the customer's local area network (LAN). In another embodiment, a cloud storage system may comprise any storage that is not housed in or directly connected to the client.
    [0084] Although three cloud storage systems are shown in Figure 2, in other implementations, there can be any number of cloud storage systems.
    [0085] Figures 4-5 are flowcharts that generally represent exemplary actions that may occur according to aspects of the subject described here. For simplicity of explanation, the methodology described in conjunction with Figures 4-5 is presented and described as a series of acts. It should be understood and appreciated that aspects of the subject matter described herein are not limited by the acts illustrated and/or the order of acts. In one embodiment, the acts occur in an order as described below. In other modalities, however, the acts may occur in parallel, in another order, and/or with other acts not presented and described here. Furthermore, not all the acts illustrated may be required to implement the methodology in accordance with the aspects of the subject described here. Furthermore, those skilled in the art understood and appreciated that the methodology could alternatively be represented as a series of interrelated states via a state diagram or as events.
    [0086] Figure 4 is a flowchart that generally represents exemplary actions that can occur from a customer perspective according to the aspects of the subject described here. At block 405, actions begin.
    [0087] In block 407, a determination is made as to whether a client is offline with respect to a cloud storage system. The customer is offline with respect to a cloud storage system if the customer is currently unable to communicate with the cloud storage system.
    [0088] At block 410, an indication is received from a file on a client's local file system. For example, referring to Figure 3, file manager 325 may receive an indication of a file from a browser application (not shown).
    [0089] At block 415, the file is detected as being represented by a placeholder. The placeholder 25 is stored on the local file system. The placeholder at least indicates that the contents of the file system object exist on a cloud storage system (even if this content also exists on the local file system). For example, referring to Figure 3, the file manager 325 detects that the file is represented by a placeholder that is stored in the local storage 320.
    [0090] Similar to metadata maintained for a file on the local file system, the placeholder may be inserted or otherwise referenced by the namespace of the local file system. In one implementation, a namespace registration that references a placeholder can be determined by a flag in the namespace registration. In another implementation, a namespace record that references a placeholder can be determined by examining the metadata included in or referenced by the namespace record.
    [0091] In block 420, a file system data structure may be updated depending on the operation that is requested against the file. For example, if the operation is a rename, move, delete, restore, create or copy or similar operation, a file system namespace may be updated to reflect the operation. For example, in a move operation, a local file system namespace might be updated to indicate that the file now resides in a new location in the namespace. As another example, in an erase operation, a local file system namespace may be updated to indicate that the file has been erased with a record of the erased file being stored in an erase container (e.g. the "can of garbage" from the file system) from the local file system. As another example, in a restore operation, a local file system namespace may be updated to indicate that a file has been restored from an erase container.
    [0092] In another example, the operation can be to update intrinsic or extrinsic metadata of the file. In this example, the placeholder can be updated with the changed metadata. When the intrinsic or extrinsic metadata of the file is changed, the local file system namespace may remain the same.
    [0093] As yet another example, an operation might be to update the contents of the file. In this example, if the placeholder indicates that the content is available locally, the content can be updated.
    [0094] In another example, there may be no need to update a file system data structure. For example, if the operation is to read a filename, the name can be read from the placeholder and provided to the requestor of the read operation. This type of operation does not involve changing the file system data structures so block 420 actions can be omitted in this example.
    [0095] In block 425, a determination is made as to whether the client is still offline. For example, referring to Figure 3, if the customer is still unable to communicate with the cloud storage system that includes the content of a placeholder, the customer can be considered offline with respect to the cloud storage system.
    [0096] At block 430, if the client is still offline with respect to the cloud storage system, actions continue at block 410 where the client may receive an indication of another file; otherwise, shares remain in block 435.
    [0097] In block 435, changes made to the local storage system while the client was offline are discovered. As indicated earlier, this discovery can take the form of reading a log of operations, comparing the file system state from a time before the changes to the file system state at the time after the changes, or the like.
    [0098] At block 440, changes are synced to the cloud storage system. For example, referring to Figure 3, the sync manager 326 can sync changes to one or more of the cloud storage systems 315-317. For example, when an offline change involves a file's intrinsic metadata, synchronization might include providing the placeholder metadata to the cloud storage system by updating the file system object's intrinsic metadata that exists in the cloud storage system.
    [0099] As another example, when the offline move involves restoring the file from an erase container, synchronization may include providing the cloud storage system with an identifier that identifies the file system object to the storage system. file together with an instruction to the cloud storage system to restore the file system object from a cloud storage system erase container.
    [00100] In block 445, other actions, if any, can be performed. For example when the client interacts with a browser application, the client may receive metadata requests for file system objects within a local file system namespace. To respond to requests that involve files that lack content that is available on the cloud storage system (e.g. files that are represented by placeholders) and to respond to requests that involve files that have their entire content available in space placeholder, the client can get the metadata of the placeholders to provide for the navigation application.
    [00101] As another example, periodically, or at other designated times, placeholders may be created for files from a local file system namespace for which the content is not entirely stored on the local file system. When connectivity is available, metadata and other data for the placeholders can be downloaded from the cloud storage system so that the local file system namespace has locally stored metadata for each file system object indicated by the namespace.
    [00102] As another example, the client can detect that an operation (eg open, edit, or similar) is not allowed when the client is offline and reject the operation if the client is offline. An exception to reject the operation while offline might occur if the placeholder indicates that the contents of the file system object are stored on the local file system.
    [00103] Figure 5 is a flowchart that generally represents exemplary actions that can occur from the perspective of a cloud storage system according to the aspects of the subject described here. At block 505, actions begin.
    [00104] At block 510, connectivity is lost between a cloud storage system and a client. For example, referring to Figure 3, the client 305 may lose connectivity to (e.g., be unable to communicate with) the cloud storage system 315. The client may have a client file system stored locally on the client (e.g. , in local storage 320). The client file system can have files where all content is located on the client file system and files where less than all content is located on the client file system. The client has at least placeholders representing the files in which less than all content is located on the client file system. The client may allow a first set of operations (e.g., one or more of renaming, moving, viewing, deleting, storing, creating, viewing metadata, updating metadata, and the like) to proceed on the files represented by the placeholders during a period when the customer is offline with respect to the cloud storage system. The client may reject a second set of operations (eg, one or more of renaming or moving through namespaces, copying, opening, editing, and the like) to proceed on files during the period when the client is offline.
    [00105] At block 515, connectivity is recovered between the client and the cloud storage system. For example, referring to Figure 3, the cloud storage system 315 may regain connectivity to (e.g., be able to communicate with) the client 305.
    [00106] At block 520, synchronization can begin. For example, referring to Figure 3, the client 305 and the cloud storage system 315 can begin to synchronize updates that occurred while the client was offline.
    [00107] In block 525, a change is received that has occurred to a file that is represented by a placeholder stored on a client's file system. The change may have occurred after customer connectivity was lost and before customer connectivity was regained. The change may be reflected in the client file system at least in part through the space reserved during a period of loss of connectivity. For example, referring to Figure 3, the cloud storage system 315 receives a change from the sync manager 326 from the client 305.
    [00108] At block 530, the cloud storage system is updated as appropriate to reflect the change. For example, referring to Figure 3, cloud storage system 315 may update file system metadata and/or metadata associated with one or more files. In some cases, changes to the cloud storage system can cause a change received from the customer to be discarded. For example, a file that was deleted on the client might also have been deleted on the cloud storage system during the period without connectivity.
    [00109] In block 535, other actions, if any, can be performed.
    [00110] As can be seen from the detailed description above, aspects have been described concerning file system placeholders. While aspects of the subject matter described herein are susceptible to various modifications and alternative constructions, certain of their illustrated embodiments are shown in the drawings and have been described in detail above. It should be understood, however, that there is no intention to limit the aspects of the claimed subject matter to the specific forms described, but rather, the intention is to cover all modifications, alternative constructions, and equivalents that fall within the spirit and scope of the various aspects. of the subject described here.
    权利要求:
    Claims (20)
    [0001]
    1. Method implemented at least in part by a computer, the method characterized in that it comprises the steps of: receiving an indication of a file system object from a client's local file system, wherein the file system local is controlled and managed by a local file system manager on the computer, where the local file system comprises a local namespace controlled and managed by the local file system, where the local file system stores file system objects local file and stores placeholders that represent respective remote file system objects, where placeholders and file system objects have respective entries in the local namespace, and where each placeholder contains a respective location of a resource resource. network of a respective remote file system object, the remote file system object configured to sync bidirectionally with a network spective local file system object represented by its placeholder; based on receipt of the indication, detect that the file system object is represented by a placeholder stored on the local file system, the placeholder indicating at least that the contents of the corresponding file system objects exist on a storage system remote, the placeholder containing a respective network resource location of a respective remote file system object with which the local file system object synchronizes; determining that the client is offline with respect to the remote storage system, the client determined to be offline with respect to the remote storage system based on the client being unable to communicate with the remote storage system; based on the determination that the client is offline, perform actions, the actions comprising: while the client is offline, update a file system data structure of the local file system to indicate an operation performed on the file system object through from the local file system while the client is offline; after the upgrade, determine that the client is no longer offline with respect to the remote storage system, and based on the determination: discover a change that occurred to the file system object while the client was offline, the change having occurred as a result of the operation; and synchronizing the change with the remote storage system by using the network resource location in the placeholder to update the remote file system object as indicated by the operation performed on the file system object.
    [0002]
    2. Method according to claim 1, characterized in that updating a file system data structure of the local file system to indicate an operation performed on the file system object comprises updating the metadata stored by the placeholder, the placeholder metadata corresponding to the file system object's intrinsic file system metadata; and wherein synchronizing the change with the remote storage system comprises providing the file system metadata to the remote storage system to update the corresponding intrinsic file system metadata of the file system object that exists on the remote storage system.
    [0003]
    3. Method according to claim 1, characterized in that updating a file system data structure of the local file system to indicate an operation performed on the file system object comprises updating the data structure of the local file system. file to indicate that the file system object was restored from an erase container; and wherein synchronizing the change to the remote storage system comprises providing the remote storage system with an identifier that identifies the file system object to the remote storage system together with an instruction to the remote storage system to restore the file system object from a remote storage system erase container.
    [0004]
    4. Method according to claim 1, characterized in that it further comprises: interacting, on the client, with a browser application that requests metadata for file system objects within a file system namespace of the local file system; and using placeholders stored on the local file system to provide metadata for browsing requests involving file system objects within the file system namespace that, on the local file system, lack content that is available on the system of remote storage.
    [0005]
    5. Method according to claim 1, characterized in that it further comprises: creating placeholders for file system objects from a namespace in the local file system for which the content is not entirely stored in the file system local file; from the remote storage system, download and store metadata to the placeholders so that the local file system namespace has locally stored metadata for each file system object indicated by the namespace; and from the remote storage system, obtain thumbnail data for each of one or more of the placeholders and store each thumbnail data in a corresponding placeholder, the thumbnail data indicating a service from which the data corresponding to an image thumbnails can be obtained.
    [0006]
    6. Method according to claim 1, characterized in that discovering a change that occurred in the file system object while the client was offline comprises searching an operations log that stores data indicating operations that occurred to system objects file from the local file system.
    [0007]
    7. Method according to claim 1, characterized in that discovering a change that occurred in the file system object while the client was offline comprises comparing a previous state of the file system objects of the local file system that occurred while the client was not offline with a changed state of file system objects from the local file system that occurred after the change.
    [0008]
    8. Method according to claim 1, characterized in that updating a file system data structure of the local file system to indicate an operation performed on the file system object comprises updating a file system namespace local if the operation is a move, delete, restore, create, or copy operation; and wherein synchronizing the change with the remote storage system comprises updating the namespace of the remote storage system according to the as-updated namespace of the local file system.
    [0009]
    9. Method, according to claim 1, characterized in that it also comprises detecting if the operation is allowed if the client is offline and does not allow the operation, if the operation is not allowed and the client is offline.
    [0010]
    10. Method according to claim 1, characterized in that it further comprises allowing the file system object to be edited while the client is offline if the placeholder indicates that the content of the file system object is stored on the local file system.
    [0011]
    11. Method according to claim 1, characterized in that the placeholder includes a name, size, modified date, and created date of the file system object.
    [0012]
    12. Method according to claim 11, characterized in that the placeholder still includes intrinsic metadata of the file system object.
    [0013]
    13. Method according to claim 1, characterized in that the content in the remote storage system comprises a structured document consisting of text in a structured format, and in which the placeholder still includes the text without the structured format.
    [0014]
    14. Method according to claim 1, characterized in that the placeholder includes a data structure that indicates portions of the file system object's content that are stored in the local file system and indicates portions of the object's content file system files that are stored on the remote storage system but not stored on the local file system.
    [0015]
    15. Computing device, characterized in that it comprises: a storage that stores a local file system maintained and controlled on the computing device, the local file system having a corresponding local namespace, the storage having storage elements in computer that maintains file system metadata for the local file system's local file system objects and that maintains placeholders for remote file system objects from a remote storage system, where the placeholders are represented in space of local name, the placeholders including metadata of the remote file system objects without requiring the contents of the remote file system objects to exist in storage, the metadata of each placeholder including an indicator that indicates whether the placeholder should be made available while offline, each placeholder containing a respective location of r ede, each network location comprising at least a respective network address and a file path of a corresponding remote file system object; a structured placeholder manager to create, populate, and maintain placeholders to ensure that a placeholder exists for each remote file system object in the local namespace at least if the contents of the remote file system object do not exist completely in storage; and a structured file system manager to control and manage, through the file system metadata and placeholders, the local namespace for the local file system, where the local namespace includes entries for the respective objects of local file system and entries for the placeholders representing the objects of the remote file system, the file system manager still structured to provide, through an interface, the metadata for the objects of the local file system and the objects file system regardless of whether connectivity exists on the remote storage system, where the file system manager is still configured to determine whether to automatically fill a placeholder with file data from a remote file system object match based on an indicator value in the placeholder.
    [0016]
    16. Computing device, according to claim 15, characterized in that it further comprises a synchronization manager structured to discover a change that has occurred with the file system object in the absence of connectivity to the remote storage system and, when connectivity is re-established with the remote storage system, to synchronize the change with the remote storage system.
    [0017]
    17. Computing device according to claim 15, characterized in that the file manager is further structured to update the file system data structure comprising the file manager being structured to update the namespace to reflect the operation during the absence of connectivity to the remote storage system if the operation is a rename, move, delete, restore, create, or copy operation.
    [0018]
    18. Computing device according to claim 15, characterized in that the placeholder manager is structured to determine the creation of a placeholder in response to the determination that a corresponding remote file system object is included in the namespace and has no content stored in storage, and where the placeholder is created before the corresponding remote file system object has been requested from the compute device.
    [0019]
    19. Computer storage medium, which has a method characterized in that it comprises: losing connectivity to a client that has a client file system stored and maintained on it, the client file system having file system objects in which all content is located in the client file system and having file system objects in which less than all of the same content is located in the client file system, the client having at least placeholders representing the objects of file system for which less than all of the content is located on the client file system, placeholders comprising respective remote file system locations of respective remote file system objects, placeholders included in a file system namespace client file system, at least some of the placeholders comprising content indications indicating which portions content are not stored on the client file system, the client allowing a first set of operations to proceed on the file system objects represented by the placeholders during a period when the client is offline with respect to the remote storage system, the client rejecting a second set of operations on file system objects during the period; regain connectivity to the client and during connectivity the client allows the second set of operations on the file system objects; during synchronization, perform actions, which include: receiving a change that has occurred on a file system object that is represented by a placeholder stored on the client file system, the change occurring after the loss of connectivity to the client and before the recovery of connectivity to the client, the change being reflected in the client file system at least in part through the reserved space during a period of loss of connectivity; and based on receipt of the change, use the remote file system location in the placeholder to update the remote storage system to reflect the change.
    [0020]
    20. Computer storage medium according to claim 19, characterized in that the change affects the namespace of the client file system, the change being reflected in the client file system through the space reserved during the connectivity loss period.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112015027040B1|2022-01-25|Method, computing device and computer storage medium
    US10264039B2|2019-04-16|Streaming content and placeholders
    US9734158B2|2017-08-15|Searching and placeholders
    KR102128138B1|2020-06-29|Hydration and dehydration with placeholders
    US10397319B2|2019-08-27|Server-side selective synchronization
    US10210191B2|2019-02-19|Accelerated access to objects in an object store implemented utilizing a file storage system
    US8601147B2|2013-12-03|Export of metadata streams to applications
    US20180329905A1|2018-11-15|Metadata Storage For Placeholders In A Storage Virtualization System
    TW201804343A|2018-02-01|Method for generating search index and server utilizing the same
    US20200104391A1|2020-04-02|Ensuring integrity of records in a not only structured query language database
    US10776376B1|2020-09-15|Systems and methods for displaying search results
    同族专利:
    公开号 | 公开日
    CA2907990A1|2014-11-06|
    CN105493077A|2016-04-13|
    JP6248182B2|2017-12-13|
    EP2992455A1|2016-03-09|
    RU2015146741A|2017-05-10|
    BR112015027040A8|2020-01-14|
    US9552363B2|2017-01-24|
    US20140324776A1|2014-10-30|
    AU2013388039B2|2019-01-31|
    CN105493077B|2019-03-19|
    CA2907990C|2020-04-07|
    RU2646334C2|2018-03-02|
    JP2016520919A|2016-07-14|
    WO2014178896A1|2014-11-06|
    KR20160004285A|2016-01-12|
    AU2013388039A1|2015-10-22|
    MX352446B|2017-11-24|
    KR102128139B1|2020-06-29|
    MX2015015145A|2016-02-18|
    BR112015027040A2|2017-07-25|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US5537585A|1994-02-25|1996-07-16|Avail Systems Corporation|Data storage management for network interconnected processors|
    EP0713183A3|1994-11-18|1996-10-02|Microsoft Corp|Network independent file shadowing|
    US20060129627A1|1996-11-22|2006-06-15|Mangosoft Corp.|Internet-based shared file service with native PC client access and semantics and distributed version control|
    AU6037198A|1997-01-27|1998-08-26|Benjamin Slotznick|System for delivering and simultaneously displaying primary and secondary information, and for displaying only the secondary information during interstitial space|
    US7373391B2|2000-10-24|2008-05-13|Seiko Epson Corporation|System and method for digital content distribution|
    US6868424B2|2002-07-25|2005-03-15|Xerox Corporation|Electronic filing system with file-placeholders|
    AU2003262965A1|2002-08-30|2004-03-19|Arkivio, Inc.|Techniques for moving stub files without recalling data|
    US20040267812A1|2003-06-26|2004-12-30|Microsoft Corporation|Media platform|
    RU2371757C2|2003-08-21|2009-10-27|Майкрософт Корпорейшн|Systems and methods of data modelling in storage platform based on subjects|
    RU2412461C2|2003-08-21|2011-02-20|Майкрософт Корпорейшн|Systems and methods of interfacing application programs with article based storage platform|
    US7441011B2|2003-10-23|2008-10-21|Microsoft Corporation|Truth on client persistent caching|
    US8108483B2|2004-01-30|2012-01-31|Microsoft Corporation|System and method for generating a consistent user namespace on networked devices|
    US7568042B2|2004-03-18|2009-07-28|Sony Corporation|Networked local media cache engine|
    US7698516B2|2005-01-12|2010-04-13|Emc Corporation|Methods and apparatus for managing deletion of data|
    US7720890B2|2005-02-22|2010-05-18|Microsoft Corporation|Ghosted synchronization|
    US20060200570A1|2005-03-02|2006-09-07|Nokia Corporation|Discovering and mounting network file systems via ad hoc, peer-to-peer networks|
    US7725837B2|2005-03-31|2010-05-25|Microsoft Corporation|Digital image browser|
    US7634514B2|2005-05-09|2009-12-15|Microsoft Corporation|Synchronizing file system directories|
    US8020158B2|2005-12-17|2011-09-13|Intel Corporation|Installing and executing shared applications in shared folders|
    US8417746B1|2006-04-03|2013-04-09|F5 Networks, Inc.|File system management with enhanced searchability|
    JP5082310B2|2006-07-10|2012-11-28|日本電気株式会社|Data migration apparatus and program|
    CN100498781C|2006-08-11|2009-06-10|中国科学院计算技术研究所|Method for storing metadata of logic document system by adhesion property|
    US7603397B1|2006-10-03|2009-10-13|Emc Corporation|Detecting and managing missing parents between primary and secondary data stores|
    NZ578689A|2007-02-05|2011-10-28|Moonwalk Universal Pty Ltd|Managing data using only data channel stateless server agents and no stateful middleware|
    US8176409B2|2007-07-24|2012-05-08|De Novo Software|System and method for electronic publication of scientific data and analysis|
    US8583878B2|2008-01-02|2013-11-12|Sandisk Il Ltd.|Storage device having direct user access|
    US8065381B2|2008-01-25|2011-11-22|Microsoft Corporation|Synchronizing for directory changes performed while offline|
    US7958167B2|2008-03-05|2011-06-07|Microsoft Corporation|Integration of unstructed data into a database|
    US20100100561A1|2008-10-15|2010-04-22|Workscape, Inc.|Benefits management for enterprise-level human capital management|
    US8468070B1|2009-04-16|2013-06-18|Amazon Technologies, Inc.|Local rendering in lieu of streaming|
    BRPI1010897A2|2009-05-19|2019-02-19|Nholdings Sa|method and system for providing a local device with computer services from a remote provider and method and system for advertising a user of a virtual machine hosted by a remote server|
    KR101626117B1|2009-06-22|2016-05-31|삼성전자주식회사|Client, brokerage sever and method for providing cloud storage|
    US10496608B2|2009-10-28|2019-12-03|Sandisk Il Ltd.|Synchronizing changes in a file system which are initiated by a storage device and a host device|
    US8612423B2|2010-10-29|2013-12-17|Microsoft Corporation|Search cache for document search|
    US9824091B2|2010-12-03|2017-11-21|Microsoft Technology Licensing, Llc|File system backup using change journal|
    US20120158891A1|2010-12-21|2012-06-21|Microsoft Corporation|Techniques for universal representation of digital content|
    US8910149B2|2010-12-24|2014-12-09|Microsoft Corporation|On-demand or incremental remote data copy|
    JP2012174113A|2011-02-23|2012-09-10|Hitachi Ltd|File storage system and storage control method|
    US8812662B2|2011-06-29|2014-08-19|Sonic Ip, Inc.|Systems and methods for estimating available bandwidth and performing initial stream selection when streaming content|
    US20130036135A1|2011-08-04|2013-02-07|Michael Brockey|Cloud data storage|
    US10063430B2|2011-09-09|2018-08-28|Cloudon Ltd.|Systems and methods for workspace interaction with cloud-based applications|
    JP5552720B2|2011-09-29|2014-07-16|ビッグローブ株式会社|Storage system, storage server, user data sharing method, and program|
    US8331566B1|2011-11-16|2012-12-11|Google Inc.|Media transmission and management|
    US20140250069A1|2013-03-01|2014-09-04|Appsense Limited|Systems and methods for selectively synchronizing files|US9405767B2|2013-05-01|2016-08-02|Microsoft Technology Licensing, Llc|Streaming content and placeholders|
    US20160147788A1|2014-11-20|2016-05-26|Ricoh Company, Ltd.|Pre-synchronization analysis between local documents and an online document management system|
    US10831715B2|2015-01-30|2020-11-10|Dropbox, Inc.|Selective downloading of shared content items in a constrained synchronization system|
    US9753943B1|2015-03-31|2017-09-05|EMC IP Holding Company LLC|Techniques for distributing access to filesystems through multipe filesystem management nodes|
    US9479567B1|2015-10-29|2016-10-25|Dropbox, Inc.|Synchronization protocol for multi-premises hosting of digital content items|
    US10140461B2|2015-10-30|2018-11-27|Microsoft Technology Licensing, Llc|Reducing resource consumption associated with storage and operation of containers|
    US9934303B2|2016-04-25|2018-04-03|Dropbox, Inc.|Storage constrained synchronization engine|
    US10049145B2|2016-04-25|2018-08-14|Dropbox, Inc.|Storage constrained synchronization engine|
    US10719532B2|2016-04-25|2020-07-21|Dropbox, Inc.|Storage constrained synchronization engine|
    WO2017187311A1|2016-04-25|2017-11-02|Dropbox, Inc.|Storage constrained synchronization engine|
    US10762054B2|2016-07-22|2020-09-01|Microsoft Technology Licensing, Llc|Cloud content states determination logic|
    US10592470B2|2016-08-10|2020-03-17|Microsoft Technology Licensing, Llc|Discovery of calling application for control of file hydration behavior|
    US10996897B2|2016-08-25|2021-05-04|Microsoft Technology Licensing, Llc|Storage virtualization for directories|
    CN107783854B|2016-08-29|2021-08-20|华为技术有限公司|Method and device for processing progress|
    US10616327B2|2016-09-20|2020-04-07|Microsoft Technology Licensing, Llc|Policy based hydration behavior in cloud storage synchronization|
    US10248659B2|2016-10-04|2019-04-02|International Business Machines Corporation|Consistent hashing configurations supporting multi-site replication|
    US10572317B2|2016-12-27|2020-02-25|Dropbox, Inc.|Collaboration enhanced with kernel event triggers|
    US10866963B2|2017-12-28|2020-12-15|Dropbox, Inc.|File system authentication|
    US11010408B2|2018-06-01|2021-05-18|Microsoft Technology Licensing, Llc|Hydration of a hierarchy of dehydrated files|
    CN111278010A|2020-01-21|2020-06-12|北京佰才邦技术有限公司|Information backup method and device, storage medium and computer equipment|
    法律状态:
    2017-08-08| B08F| Application dismissed because of non-payment of annual fees [chapter 8.6 patent gazette]|
    2017-10-10| B08G| Application fees: restoration [chapter 8.7 patent gazette]|
    2018-11-21| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2020-02-11| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2021-07-13| B350| Update of information on the portal [chapter 15.35 patent gazette]|
    2021-11-16| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2022-01-25| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 18/09/2013, OBSERVADAS AS CONDICOES LEGAIS. |
    优先权:
    申请号 | 申请日 | 专利标题
    US13/873,241|2013-04-30|
    US13/873,241|US9552363B2|2013-04-30|2013-04-30|File management with placeholders|
    PCT/US2013/060250|WO2014178896A1|2013-04-30|2013-09-18|File management with placeholders|
    [返回顶部]